Grokking SQL for Tech Interviews
Rate this course
Ask Author
Contribute
Back to course home

1% completed

Vote For New Content
Introduction
Course Overview
What is RDBMS?
What is SQL?
A Quick Review of SQL
Read data from table
WHERE Clause
Operators
Handle NULLs in SQL
DISTINCT Clause
ORDER BY Clause
LIMIT and OFFSET
GROUP BY
HAVING
Aggregate Functions
Order of Execution
Order of SQL Query Execution
SQL Functions
Number Functions
String Functions
Date Functions
Nested Queries
Nested Query
Types of Subqueries
JOINS
Introduction
INNER JOIN
LEFT OUTER JOIN
RIGHT OUTER JOIN
FULL OUTER JOIN
SELF JOIN
SET Operations
What are SET operations?
UNION
INTERSECT
EXCEPT
A Quick Review of DDL
Keys in SQL
CREATE
ALTER
DROP
TRUNCATE
Indexes
A Quick Review of DML
INSERT
UPDATE
DELETE
Database Backup & Restore
Backup Database
Restore Database
Interview Problems - Easy
1. Major Cities
2. Not boring movies
3. Triangle Judgement
4. Biggest Single Number
5. Product Sales Analysis I
6. Product Sales Analysis II
7. Game Play Analysis I
8. Game Play Analysis II
9. Queries Quality and Percentage
10. Average Selling Price
11. Weather Type in Each Country
12. Students and Examinations
13. Ads Performance
14. Group Sold Products By The Date
15. Employee Email Verification
16. Sellers With No Sales
17. Average Time of Process
18. Find Followers Count
19. Ad-Free Sessions
20. Bikes Last Time Used
21. Daily User Engagement Levels
22. Employee Attendance Record
23. Library Book Loans
24. Customer Purchase Summary
25. Long Comments (Easy)
26. Unused Accounts
27. Patient Appointment No-Shows
28. Books and Authors
29. High School Attendance
30. Employee Absences
31. Green Product Identification (Easy)
32. Employee Department Exclusion (Easy)
33. Sales Person (Easy)
34. Employee Task Tracking (Easy)
Interview Problems - Medium
1. Winning Candidate
2. Second Degree Follower
3. 2nd Highest Salary
4. Game Play Analysis III
5. Game Play Analysis IV
6. Active Businesses
7. Product Price on a Specific Date
8. Monthly Transactions II
9. Team Scores in Football Tournament
10. Page Recommendations
11. Running Total for Different Genders
12. Evaluate Boolean Expression
13. Active Users
14. Find Interview Candidates
15. Suspicious Bank Accounts
16. Order Fulfillment Rate (Medium)
17. Last Person to Fit in the Elevator (Medium)
18. Retail Expansion Analysis (Medium)
19. Employee Collaboration Networks (Medium)
20. Second Fastest Time in Races (Medium)
Interview Problems - Hard
1. Trips and Users
2. Human Traffic of Stadium
3. Students Report By Geography
4. Game Play Analysis V
5. Number of Transactions per Visit
6. Find the Quiet Students in All Exams
7. First and Last Call On the Same Day
8. Build the Equation
9. Longest Winning Streak
10. Dynamic Pivoting of a Table
11. Dynamic Unpivoting of a Table
12. Generate the Invoice
13. Popularity Percentage
14. Viewers Turned Streamers
15. Status of Flight Tickets
1. High Performing Employees (Easy)
2. Student Course Averages (Easy)
3. Library Book Checkout Percentage (Easy)
4. Employee Performance and Improvement Rate (Easy)
5. Find Popular Posts (Easy)
6. Main Office Assignment for Each Employee (Easy)
7. Rectangle Validation (Easy)
8. Library Book Checkouts by Date (Easy)
9. Same-Day Appointment Fulfillment (Medium)
10. Departments with High Earning Employees (Medium)
11. Students Who Attended All Courses (Medium)
12. Library Book Checkouts First Year (Medium)
13. Repeated Values in Sequence (Medium)
14. School Top Achievers by Subject (Hard)
1. Trips and Users

Problem

Table: Trips

+-------------+----------+
| Column Name | Type     |
+-------------+----------+
| id          | int      |
| client_id   | int      |
| driver_id   | int      |
| city_id     | int      |
| status      | enum     |
| request_at  | date     |     
+-------------+----------+
id is the primary key (column with unique values) for this table.
The table holds all taxi trips. Each trip has a unique id, while client_id and driver_id are foreign keys to the users_id at the Users table.
Status is an ENUM (category) type of ('completed', 'cancelled_by_driver', 'cancelled_by_client'). 

Table: Users

+-------------+----------+
| Column Name | Type     |
+-------------+----------+
| users_id    | int      |
| banned      | enum     |
| role        | enum     |
+-------------+----------+
users_id is the primary key (column with unique values) for this table.
The table holds all users. Each user has a unique users_id, and role is an ENUM type of ('client', 'driver', 'partner').
banned is an ENUM (category) type of ('Yes', 'No').

Problem Definition

The cancellation rate is computed by dividing the number of canceled (by client or driver) requests with unbanned users by the total number of requests with unbanned users on that day.

Write a solution to find the cancellation rate of requests with unbanned users (both client and driver must not be banned) each day between "2013-10-01" and "2013-10-03". Round Cancellation Rate to two decimal points.

Example

Image

Output

Image

Try It Yourself

MYSQL

. . . .

Trips =

Users =

Solution

To calculate the cancellation rate of taxi trip requests with unbanned users between "2013-10-01" and "2013-10-03", we need to analyze the Trips and Users tables. The cancellation rate is defined as the ratio of the number of canceled trips (either canceled by the client or the driver) to the total number of trip requests, considering only those trips where both the client and the driver are not banned.

Approach Overview

  1. Filter Unbanned Users:

    • Clients: Exclude trips where the client_id corresponds to a banned user.
    • Drivers: Exclude trips where the driver_id corresponds to a banned user.
  2. Filter by Date Range:

    • Consider only trips with request_at dates between "2013-10-01" and "2013-10-03".
  3. Calculate Cancellation Rate:

    • Numerator: Count of trips with status 'cancelled_by_driver' or 'cancelled_by_client'.
    • Denominator: Total number of trips (including both completed and canceled) within the specified date range and with unbanned users.
    • Cancellation Rate: (Number of Canceled Trips) / (Total Number of Trips) rounded to two decimal places.
  4. Present the Results:

    • Display the Day and the corresponding Cancellation Rate in the specified format.

SQL Query

SELECT request_at AS Day, Round(SUM(IF(status = 'completed', 0, 1)) / Count(status), 2) AS 'Cancellation Rate' FROM Trips WHERE client_id NOT IN (SELECT users_id FROM Users WHERE banned = 'Yes') AND driver_id NOT IN (SELECT users_id FROM Users WHERE banned = 'Yes') AND request_at BETWEEN '2013-10-01' AND '2013-10-03' GROUP BY request_at;

Step-by-Step Approach

We'll break down the SQL query into smaller steps to understand how the Cancellation Rate is calculated. For illustration purposes, we'll use the provided sample data.

Step 1: Identify Unbanned Users

Filter out trips where either the client or the driver is banned.

SQL:

SELECT * FROM Trips WHERE client_id NOT IN ( SELECT users_id FROM Users WHERE banned = 'Yes' ) AND driver_id NOT IN ( SELECT users_id FROM Users WHERE banned = 'Yes' );

Explanation:

  • client_id NOT IN (...) and driver_id NOT IN (...):
    • Ensures that both the client and the driver associated with a trip are not banned.

Intermediate Output After Step 1:

+----+-----------+-----------+---------+-----------------------+------------+ | id | client_id | driver_id | city_id | status | request_at | +----+-----------+-----------+---------+-----------------------+------------+ | 1 | 1 | 10 | 1 | completed | 2013-10-01 | | 3 | 3 | 12 | 6 | completed | 2013-10-01 | | 4 | 4 | 13 | 6 | cancelled_by_driver | 2013-10-01 | | 5 | 1 | 10 | 1 | completed | 2013-10-02 | | 6 | 2 | 11 | 6 | completed | 2013-10-02 | | 7 | 3 | 12 | 6 | completed | 2013-10-02 | | 8 | 2 | 12 | 12 | completed | 2013-10-03 | | 9 | 3 | 10 | 12 | completed | 2013-10-03 | | 10 | 4 | 13 | 12 | cancelled_by_driver | 2013-10-03 | +----+-----------+-----------+---------+-----------------------+------------+

Note:

  • Trips with client_id = 2 are excluded because user 2 is banned (banned = 'Yes').

Step 2: Filter Trips Within the Date Range

Consider only trips that occurred between "2013-10-01" and "2013-10-03".

SQL:

SELECT * FROM Trips WHERE client_id NOT IN ( SELECT users_id FROM Users WHERE banned = 'Yes' ) AND driver_id NOT IN ( SELECT users_id FROM Users WHERE banned = 'Yes' ) AND request_at BETWEEN '2013-10-01' AND '2013-10-03';

Explanation:

  • request_at BETWEEN '2013-10-01' AND '2013-10-03':
    • Limits the analysis to trips within the specified date range.

Intermediate Output After Step 2:

+----+-----------+-----------+---------+-----------------------+------------+ | id | client_id | driver_id | city_id | status | request_at | +----+-----------+-----------+---------+-----------------------+------------+ | 1 | 1 | 10 | 1 | completed | 2013-10-01 | | 3 | 3 | 12 | 6 | completed | 2013-10-01 | | 4 | 4 | 13 | 6 | cancelled_by_driver | 2013-10-01 | | 5 | 1 | 10 | 1 | completed | 2013-10-02 | | 6 | 2 | 11 | 6 | completed | 2013-10-02 | | 7 | 3 | 12 | 6 | completed | 2013-10-02 | | 8 | 2 | 12 | 12 | completed | 2013-10-03 | | 9 | 3 | 10 | 12 | completed | 2013-10-03 | | 10 | 4 | 13 | 12 | cancelled_by_driver | 2013-10-03 | +----+-----------+-----------+---------+-----------------------+------------+

Step 3: Calculate Cancellation Rate Per Day

Compute the Cancellation Rate for each day by dividing the number of canceled trips by the total number of trips for that day. Only consider trips where both the client and driver are not banned.

SQL:

SELECT request_at AS Day, Round(SUM(IF(status = 'completed', 0, 1)) / Count(status), 2) AS 'Cancellation Rate' FROM Trips WHERE client_id NOT IN ( SELECT users_id FROM Users WHERE banned = 'Yes' ) AND driver_id NOT IN ( SELECT users_id FROM Users WHERE banned = 'Yes' ) AND request_at BETWEEN '2013-10-01' AND '2013-10-03' GROUP BY request_at;

Explanation:

  • SUM(IF(status = 'completed', 0, 1)):
    • Counts the number of canceled trips (status not equal to 'completed').
  • Count(status):
    • Counts the total number of trips for that day.
  • Round(..., 2):
    • Rounds the cancellation rate to two decimal places.
  • GROUP BY request_at:
    • Calculates the cancellation rate for each day separately.

Final Output:

+--------------------------+-------------------+ | Day | Cancellation Rate | +--------------------------+-------------------+ | 2013-10-01T00:00:00.000Z | 0.33 | | 2013-10-02T00:00:00.000Z | 0.00 | | 2013-10-03T00:00:00.000Z | 0.50 | +--------------------------+-------------------+

Explanation of Output:

  • 2013-10-01:
    • Cancellation Rate: 0.33 (1 canceled trip out of 3)
  • 2013-10-02:
    • Cancellation Rate: 0.00 (0 canceled trips out of 3)
  • 2013-10-03:
    • Cancellation Rate: 0.50 (2 canceled trips out of 4)
20. Second Fastest Time in Races (Medium)
2. Human Traffic of Stadium
Mark as Completed

On this page

Problem

Problem Definition

Example

Output

Try It Yourself

Solution

Approach Overview

SQL Query

Step-by-Step Approach

Final Output: